@guicassolato so this works for your use-case(s)?
Also, that last test is somewhat sad... wdy'all think?

@eguzki is this ok? Or are you still expecting more changes?

So reading this:

// If a query param is repeated in an HTTP request, the behavior is
// purposely left undefined, since different data planes have different
// capabilities. However, it is *recommended* that implementations should
// match against the first value of the param if the data plane supports it,
// as this behavior is expected in other load balancing contexts outside of
// the Gateway API.
//
// Users SHOULD NOT route traffic based on repeated query params to guard
// themselves against potential differences in the implementations.

Wondering if we shouldn't always have the first param in our Map and drop the List altogether...
I have a PR getting ready that would:

fmt.Sprintf("decodeQueryString(request.query)['%s'] == '%s'", queryParam.Name, queryParam.Value)

@guicassolato do you have an opinion?

Alternate proposal, that I'll implement here right now, pass an optional 2nd bool param, that would dictate whether to return a List when repeated params are present, or only the first one (includeRepeatedParams: bool kinda thing).

See this PR on the Kuadrant Operator side

In description it says decodeQueryString but in the implementation I see queryMap.